• 6e774bb #45: bump version 4.2.4
• 02de76e Merge pull request #45 from karlhorky/patch-1
• 2175d24 Fix type for parse()
• 4416b4d README.md: update badge
• a72016b test: goodbye travis, hello github
• 9671f1b Merge pull request #40 from ambujsahu81/patch-1
• 8fe85ca Fix query comments example in readme.md
• See full diff in compare view

Sourced from promise-socket's releases.

v8.0.0

• Converted to ESM module.
• Requires Node >= 16.
• Uses "node:" prefix for Node.js modules.
• Uses promise-writable with listeners leak fixed in dex4er/js-promise-writable4; closes dex4er/js-promise-socket4.
• Uses promise-duplex with closed property that works with Node.js >= 16; closes dex4er/js-promise-socket4.
• setTimeout returns this; closes: dex4er/js-promise-socket4.

Sourced from promise-socket's changelog.

v8.0.0 2024-06-21

• Converted to ESM module.
• Requires Node >= 16.
• Uses "node:" prefix for Node.js modules.
• Uses promise-writable with listeners leak fixed in dex4er/js-promise-writable4; closes dex4er/js-promise-socket4.
• Uses promise-duplex with closed property that works with Node.js >= 16; closes dex4er/js-promise-socket4.
• setTimeout returns this; closes: dex4er/js-promise-socket4.

• b786a15 Update dependency promise-duplex to v8
• 9cebd7f Improved example
• d218628 Renovate: Typescript updates are always separate
• 0a072d2 Changelog for #63
• 1b4899c setTimeout returns this
• 440fbf6 promisify
• 2f509d5 Converted to ESM module
• See full diff in compare view

• See full diff in compare view

• See full diff in compare view

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.17.0

7.17.0 (2024-07-22)

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7 (#9507)
• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never" (#9364)

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more) (#9043)
• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context (#9074)
• eslint-plugin: [no-unnecessary-condition] false positive on optional private field (#9602)
• typescript-estree: don't infer single-run when --fix is in proces.argv (#9577)
• typescript-estree: disable single-run inference with extraFileExtensions (#9580)
• website: expose ATA types to eslint instance (#9598)

❤️ Thank You

• Armano @​armano2
• Josh Goldberg ✨
• Kirk Waiblinger @​kirkwaiblinger
• StyleShit @​StyleShit

You can read about our versioning strategy and releases on our website.

v7.16.1

7.16.1 (2024-07-15)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-parameters] descend into all parts of mapped types in no-unnecessary-type-parameters (#9530)

❤️ Thank You

• Dan Vanderkam @​danvk

You can read about our versioning strategy and releases on our website.

v7.16.0

7.16.0 (2024-07-08)

🚀 Features

• ast-spec: add parent property to AccessorProperty node types (#9487)
• eslint-plugin: [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule (#8903)

... (truncated)

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.17.0 (2024-07-22)

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7

• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more)

• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context

• eslint-plugin: [no-unnecessary-condition] false positive on optional private field

❤️ Thank You

• Armano
• Josh Goldberg ✨
• Kirk Waiblinger
• StyleShit

You can read about our versioning strategy and releases on our website.

7.16.1 (2024-07-15)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-parameters] descend into all parts of mapped types in no-unnecessary-type-parameters

❤️ Thank You

• Dan Vanderkam

You can read about our versioning strategy and releases on our website.

7.16.0 (2024-07-08)

🚀 Features

• rule-tester: stricter rule test validations

• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule

... (truncated)

• 05c9cb8 chore(release): publish 7.17.0
• f6c719f fix(eslint-plugin): [no-unnecessary-condition] false positive on optional pri...
• 6647f7e chore: enable no-unreachable-loop (#9540)
• 58be99f chore: enable prefer-object-spread (#9541)
• 5d895b7 chore: enable @​typescript-eslint/no-unused-expressions (#9542)
• d8c539d chore: enable no-useless-concat (#9550)
• f043f30 fix(eslint-plugin): [strict-boolean-expressions] consider assertion function ...
• 0108e9c chore: enable no-lonely-if (#9547)
• 970f3f1 feat(eslint-plugin): [return-await] add option to report in error-handling sc...
• dd965a4 feat(eslint-plugin): backport no-unsafe-function type, no-wrapper-object-type...
• Additional commits viewable in compare view

Sourced from @​typescript-eslint/parser's releases.

v7.17.0

7.17.0 (2024-07-22)

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7 (#9507)
• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never" (#9364)

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more) (#9043)
• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context (#9074)
• eslint-plugin: [no-unnecessary-condition] false positive on optional private field (#9602)
• typescript-estree: don't infer single-run when --fix is in proces.argv (#9577)
• typescript-estree: disable single-run inference with extraFileExtensions (#9580)
• website: expose ATA types to eslint instance (#9598)

❤️ Thank You

• Armano @​armano2
• Josh Goldberg ✨
• Kirk Waiblinger @​kirkwaiblinger
• StyleShit @​StyleShit

You can read about our versioning strategy and releases on our website.

v7.16.1

7.16.1 (2024-07-15)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-parameters] descend into all parts of mapped types in no-unnecessary-type-parameters (#9530)

❤️ Thank You

• Dan Vanderkam @​danvk

You can read about our versioning strategy and releases on our website.

v7.16.0

7.16.0 (2024-07-08)

🚀 Features

• ast-spec: add parent property to AccessorProperty node types (#9487)
• eslint-plugin: [no-unnecessary-type-parameters] port from v8 to v7 (#9473)
• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule (#8903)

... (truncated)

Sourced from @​typescript-eslint/parser's changelog.

7.17.0 (2024-07-22)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.16.1 (2024-07-15)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.16.0 (2024-07-08)

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0

• website: react key error on internal pages of website

❤️ Thank You

• Abraham Guo
• auvred
• Josh Goldberg ✨
• Juan Sanchez
• Vinccool96
• YeonJuan
• Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

7.15.0 (2024-07-01)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.14.1 (2024-06-24)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.14.0 (2024-06-24)

🚀 Features

... (truncated)

• 05c9cb8 chore(release): publish 7.17.0
• 58be99f chore: enable prefer-object-spread (#9541)
• d1d0ba5 chore(release): publish 7.16.1
• e803c50 chore(release): publish 7.16.0
• 2865d31 chore(release): publish 7.15.0
• b4fe94f chore(release): publish 7.14.1
• dfc4469 chore(release): publish 7.14.0
• 1212a8f chore(release): publish 7.13.1
• 8a178ed chore(release): publish 7.13.0
• c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
• Additional commits viewable in compare view

Sourced from @​vscode/vsce's releases.

v2.31.1

Changes:

• #1027: Update deprecated dependencies
• #1025: Don't package default readme if a path is provided and default is ignored
• #1024: add executes code property

This list of changes was auto generated.

v2.31.1-2

Changes:

• #1027: Update deprecated dependencies

This list of changes was auto generated.

v2.31.1-1

Changes:

• #1025: Don't package default readme if a path is provided and default is ignored

This list of changes was auto generated.

v2.31.1-0

Changes:

• #1024: add executes code property

This list of changes was auto generated.

v2.31.0

Changes:

• #1022: Throw error if provided readmePath or provided changelogPath could not be found
• #1020: Throw when unused files pattern in package.json
• #1015: Support "ls --tree"

This list of changes was auto generated.

v2.30.1-3

... (truncated)

• ca8fa40 Merge pull request #1027 from microsoft/benibenj/logical-duck
• d0e1a5c update depricated dependencies
• 3b1b774 Merge pull request #1025 from microsoft:benibenj/well-lion
• d83f7ba Don't package default readme if a path is provided
• 2e3e3bc add executes code property (#1024)
• dd70844 Merge pull request #1022 from microsoft/benibenj/profound-gorilla
• ff9391d Throw error if provided readmePath or provided changelogPath could not be found
• a97062f Merge pull request #1021 from microsoft/benibenj/chronic-spider
• 2c95bcb use filter functioon
• f55228d Merge pull request #1020 from microsoft/benibenj/miserable-tern
• Additional commits viewable in compare view

Sourced from esbuild's releases.

v0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

v0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012

... (truncated)

Sourced from esbuild's changelog.

0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

• Revert the recent change to avoid bundling dependencies for node (#3819)

  This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

  I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

  In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

• Fix preserving collapsed JSX whitespace (#3818)

  When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

  // Original code
  <Foo>
    <Bar />
  </Foo>
  // Old output (with --jsx=preserve)
  <Foo><Bar /></Foo>;
  // New output (with --jsx=preserve)
  <Foo>
  <Bar />
  </Foo>;

0.22.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

• Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

  This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

  With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

  The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

• Drop support for older platforms (#3802)

  This release drops support for the following operating systems:

  • Windows 7
  • Windows 8
  • Windows Server 2008

... (truncated)

• 9d50680 publish 0.23.0 to npm
• ac7fd04 Revert "fix #1874: node defaults to --packages=external" (#3820)
• 626ac2c fix #3818: preserve collapsed jsx whitespace
• 7c2eb2e hashbang syntax is part of es2023
• 80c6e6e publish 0.22.0 to npm
• 196dcad fix #1874: node defaults to --packages=external
• 3f57db8 release notes for #3539
• 91663db Provide API to create a custom esbuild CLI with plugins (#3539)
• e01c0e0 also mention #3665 in release notes
• 65711b3 release notes for #3674
• Additional commits viewable in compare view

Sourced from prettier's releases.

3.3.3

🔗 Changelog

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

Sourced from prettier's changelog.

3.3.3

diff

Add parentheses for nullish coalescing in ternary (#16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@(foo`tagged template`)
class X {}
// Prettier 3.3.2
@​footagged template
class X {}
// Prettier 3.3.3
@(footagged template)
class X {}

Support @let declaration syntax (#16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

... (truncated)

• 5282938 Release 3.3.3
• 9102b73 Add parentheses for decorator expressions (#16458)
• 6bbd461 chore(deps): update eslint related dependencies (#16478)
• 04b560f chore(deps): update dependency browserslist to v4.23.2 (#16475)
• 614f070 chore(deps): update typescript-eslint to v8.0.0-alpha.41 (#16477)
• d59a15d chore(deps): update dependency npm-run-all2 to v6.2.2 (#16476)
• 5ca2fc9 Support Angular @let declaration syntax (#16474)
• bfcfdcc chore(deps): update babel to v7.24.8 (#16472)
• 977c161 chore(deps): update dependency acorn to v8.12.1 (#16464)
• 550606e chore(deps): update babel to v7.24.8 (#16470)
• Additional commits viewable in compare view

Sourced from typescript's releases.

TypeScript 5.5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.5.0 (Beta).

... (truncated)

• c8a7d58 Bump version to 5.5.4 and LKG
• c0ded04 🤖 Pick PR #58771 (Allow references to the global Symb...) into release-5.5 (#...
• 5ba41e2 🤖 Pick PR #59208 (Write non-missing undefined on mapp...) into release-5.5 (#...
• b075332 🤖 Pick PR #59337 (Allow declarationMap to be emitted ...) into release-5.5 (#...
• 9dd6f91 Cherry-pick "Stop using latest Node in CI" to release-5.5 (#59348)
• bf0ddaf 🤖 Pick PR #59070 (Delay the calculation of common sou...) into release-5.5 (#...
• a44e2d9 🤖 Pick PR #59160 (Fixed crash on authored import type...) into release-5.5 (#...
• f35206d 🤖 Pick PR #59325 (Don't skip markLinkedReferences on ...) into release-5.5 (#...
• 1109550 Fix baselines on release-5.5 (#59330)
• 8794318 🤖 Pick PR #59215 (Fix codefix crash on circular alias...) into release-5.5 (#...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions